Skip to content

Conversation

@larskemper
Copy link
Member

@larskemper larskemper commented Dec 23, 2025

Apply the same validation strategy we use to flag bad field values during error resolution to the values the user propose as fixes. Also for JSON inputs like cart prices, show users concrete example values they can adapt.

@larskemper larskemper self-assigned this Dec 23, 2025
@larskemper larskemper marked this pull request as ready for review December 29, 2025 10:04
@larskemper larskemper marked this pull request as draft January 6, 2026 15:38
@larskemper larskemper force-pushed the feat/add-validation-of-resolution-values branch from f73931a to ec3f5da Compare January 7, 2026 13:59
@larskemper larskemper changed the base branch from feature/migration-logging-refactor to refactor/filter-optional-database-field January 7, 2026 14:00
@larskemper larskemper marked this pull request as ready for review January 7, 2026 14:01
@larskemper larskemper requested review from a team, MalteJanz, ennasus4sun and vintagesucks and removed request for a team, DennisGarding and MalteJanz January 7, 2026 14:01
@larskemper larskemper marked this pull request as draft January 8, 2026 07:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants